home *** CD-ROM | disk | FTP | other *** search
- Path: xs1.xs4all.nl!marcone
- From: marcone@xs1.xs4all.nl (Marco Nelissen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: FindTask() VERY IMPORTANT
- Date: 15 Mar 1996 08:25:04 GMT
- Organization: XS4ALL Internet
- Message-ID: <4ib9h0$i23@news.xs4all.nl>
- References: <4hp3cv$cqe@serpens.rhein.de> <4i64pk$ia1@news.xs4all.nl> <4i74pb$b4f@serpens.rhein.de>
- NNTP-Posting-Host: xs1.xs4all.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael van Elst (mlelstv@serpens.rhein.de) wrote:
- : I can only repeat myself:
-
- So I've noticed...
-
- : If there is a system function for a task then use it instead of peeking
- : data structures.
-
- SysBase->ThisTask is _R_E_A_D_A_B_L_E_, and always has been. Why shouldn't
- I use it? If this suddenly fails on a new OS, so be it, but it won't be my
- fault.
-
- : This has a reason as the function interface allows to change the data
- : structures, it also allows access policies. Is it too difficult to
- : grasp for you ?
-
- Is it too difficult for you to understand that until now SysBase->ThisTask
- has always been documented as being readble? It is perfectly legal to
- use it. Show me where it says I cannot use this field...
-
- : Peeking ThisTask serves only two purposes: to spare the few cycles for
- : the function call at the cost of compatibility and to show how c00l you
- : are because you know what the system does. Is it that what you want ?
-
- There is nothing 'cool' about using a system structure if that particular
- structure is documented readable...
- The compatibility problem you are referring to should be non-existant. If
- there is a problem, it is to blame on whoever created the new OS, since they
- deliberately introduced a compatibility-problem.
-
- Marco
-